Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0955

reference: 655-tree-1
name: 0955
tree-preservation-order: undefined
655-tpo-1
uprn
address-text
point: POINT (-1.013493 50.867474)
geometry: MULTIPOLYGON (((-1.013464 50.867471,-1.013465 50.867477,-1.013469 50.867482,-1.013483 50.867489,-1.013501 50.867489,-1.013509 50.867486,-1.013520 50.867477,-1.013521 50.867472,-1.013520 50.867466,-1.013516 50.867461,-1.013502 50.867454,-1.013484 50.867454,-1.013476 50.867457,-1.013470 50.867461,-1.013464 50.867471)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL